Internet Tools (InfoMagic)/Internet Tools.iso/dos_win/winsock/maillist/94-05.Z/94-05/[e-mail]_Wed May 25 15:30:31 1994.msg

Internet Message Format | 1994-05-31 | 17KB

Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA01038; Wed, 25 May 1994 12:55:34 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA11880; Wed, 25 May 1994 12:33:48 -0400
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 25 May 1994 15:30:31 GMT
From: [e-mail] (Ben Miller     Music Library    0004    812-855-2970)
Message-Id: <[e-mail]>
Organization: Indiana University Music Library, Bloomington
Sender: ses
Subject: Final plea for NFS

I've read the FAQ, I've spent hours out on the net through archie and
veronica and the www worm, serching but I can't seem to find an NFS app
(non-commercial) server OR client for Winsock.  I would MUCH prefer a
server as there is MUCH more disk space on the Windows machine, but a
client would be very nice indeed.

Any advice for a man about to blow a lot of money on a commercial NFS
package?

    Thanks,
        Ben
--

+---------------------------------+-----------------------------------+
|Benjamin G. Miller               |                                   |
|[e-mail] |  From square one                  |
From [e-mail] Wed May 25 03:03:00 1994
Received: from netmail2.microsoft.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA03283; Wed, 25 May 1994 13:06:38 -0400
Received:  by netmail2.microsoft.com (5.65/25-eef)
    id AA29845; Wed, 25 May 94 09:07:57 -0700
Received: by netmail2 using fxenixd 1.0 Wed, 25 May 94 09:07:57 PDT
Message-Id: <9405251705.AA16036@itgmsm>
From: [e-mail]
To: [e-mail], [e-mail]
Cc: [e-mail], [e-mail]
Subject: FW: WinSock Compliance Testing
Date: Wed, 25 May 94 10:03:00 PDT
X-Mailer: Microsoft Mail V3.0



| ----------
| From: Neil Rowland  <[e-mail]>
| To: Multiple recipients of list  <[e-mail]>
| Subject: Re: WinSock Compliance Testing
| Date: Tuesday, May 24, 1994 10:37AM
|
| >A validation suite is mentioned in the Winsock spec. it's called WSAT
| >(Windows Sockets API Tester) and is apparently available by sending
| >email to [e-mail] .  Haven't got it yet though, the ftp
| >address they gave me (in the automaic mail reply) doesn't respond.
|
| Last time I inquired about WSAT, I got a whole load of doubletalk.
| 1st, they said it was for Winsock implementors, not developers using
| winsock.  Then, they said that certain tests were "supposed to fail", and
| it took an expert to properly interpret the results, and more condes-
| cending obfuscation along that line, but still no specifics.
|

Neil,

My apologies for whatever piece of information I sent out that you found to
be "condescending obfuscation."   I've included the WSAT auto e-mail reply
below, which I believe is reasonably clear,  but I'll take a little more
time here and try to set the record on WSAT straight.

WSAT is simply a packaged up version of API tests that I wrote for testing
windows sockets in NT 3.1.  That's it.   It wasn't written to be a
compliance suite or a benchmark, it was simply a large chunk of the work I
did to help Dave Treadwell make his NT winsock implementation great.   The
reason we at microsoft felt WSAT was worth realeasing was that we obviously
have an interest in anything that helps windows, and what helps windows is
great, cool, stable windows applications.  We felt that releasing these
tests would help make various windows sockets implemenations more standard
and stable and hence a better cross platform programming environment.  I
believe (a touch of ego?) that WSAT has aided windows sockets tremendous
success.

Ok, let me again that a stab at the main point of confusion:

*** Winsock IS for winsock implemenation developers.   It is NOT a good
numerical benchmark. ***

As noted above, these are just my tests -- designed to detect errors -- NOT
a benchmark.   Hence some implementation may fail 10 variations in the
socket test, because their implementation and my interpretation of the spec
(WSAT) differ on what is the appropriate error code for socket called with a
bad protocol value.   Some other implementation, my fail ten variations in
the send test that would kill an application. If you try to benchmark these
implementations with WSAT, and consider any ten failures to be comparable,
you're fooling yourself and learning little.

Obviously if some implementation is failing a hundred variations and some
other implementation only ten, then I'd bet on the stability on the later.
  But  the point is that you'd need to look at the failures and intrepret
them and their impact on your application, to really know.    And that
brings us back to the purpose of WSAT:  to help the winsock implementor find
these errors -- if necessary, air any disagreement with me over the expected
behavior -- and fix them.

That's it.   Hopefully the confusion is removed.   WSAT continues to be
available on rhino.microsoft.com.   This is not my primary testing focus
these days, and I'm rather slow getting to them, but I will attempt to
update when giving a clear explanation of a WSAT bug.   (I recently punched
up the wsat.txt readme, and I recently fixed some accept script bugs
reported to me at the bakeoff.)

     jim

Here is the auto-mail that goes out to people who inquire:

 -----------------------------

Thank you for sending mail to [e-mail].

We are freely distributing the latest version of the tester and scripts to
winsock implementation developers for the purpose of encouraging the highest
quality winsock implementations and maximizing appilcation interoperability.

It should be noted that wsat is intended for this purpose -- helping
developers whip their winsock implementations into shape -- and is NOT
useful for winsock application developers.  Nor is WSAT a good numerical
benchmark.  The test reports results in terms of "variations", which are
simply a single item of winsock behavior that I am trying to verify.  Some
of these variations are critically important -- their failure would break
many applications -- while many others might affect no applications at all.
In addition, the variation failures many range from the catastrophic (a
crash) to trivial error code issues.  Hence, without knowledge of the
specific variation failing and the failures involved, a simple pass/fail
report from wsat gives only the grossest measure of winsock spec compliance.

The latest version of the tester and scripts are on rhino.microsoft.com via
non-anonymous FTP. Once connected to rhino.microsoft.com, use the username:
"wsat" and the password "TestWSAT".  The WSAT distribution is available as a
single zipped file, and in a subdirectory in unpacked form.  If you
encounter any problems fetching the WSAT tester from rhino, e-mail:
[e-mail].

Please read the WSAT description/instructions in wsat.txt.  If you encounter
any problems running WSAT, or have feedback for improving the tester or
scripts, e-mail [e-mail].
From [e-mail] Wed May 25 03:10:08 1994
Received: from relay1.UU.NET by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA06654; Wed, 25 May 1994 13:22:06 -0400
Received: from netmanage.com (via netman-gate.netmanage.com) by relay1.UU.NET with SMTP
    (5.61/UUNET-internet-primary) id AAwrld19241; Wed, 25 May 94 13:22:04 -0400
Received: from suzannec.netmanage.com by netmanage.com (4.1/NetManage-1.0)
    id AA06660; Wed, 25 May 94 10:13:52 PDT
Date: Wed, 25 May 94 10:10:08 PDT
From: [e-mail]
Subject: FW:  Chameleon Sampler PPP
To: [e-mail], [e-mail]
Cc: [e-mail]
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.
Message-Id: <[e-mail]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

Hello,
Our PPP in Sampler does support Van Jacobson Compression.
We got the document below from Netcom for use with Chameleon.
We do have several tips for different internet providers
on our gopher server at gopher.netmanage.com in the
Third Party Vendors and Providers\Internet Providers\
Internet Providers Survival Guides section.

***
The following are highlights of the most frequently
encountered issues using Chameleon with NetCom
dialup.  This should be the quick reference guide for
helping mutual NetManage and NetCom customers.  NetCom
has a great service, and Chameleon is a great product.
All it takes is mutual understanding for everthing to
work like a charm every single time.

Custom Application Setup in Chameleon
-------------------------------------
0. The user should have the LOG on in Custom so
   that they can see what is going on when they connect.
   This can be turned off once the user has an operational
   Custom configuration.

1. Verify that the user has defined an interface in
   Custom that corresponds to the one assigned by Netcom.

   Note: SLIP, CSLIP, and PPP interfaces in the Chameleon
   Custom application are not interchangeable, and NetCom
   sets up users' accounts to expect one or the other. The
   user needs to initially add the correct type of interface.
   Interfaces cannot be changed by simply editing the Type field.

   The pre-configured Custom setup for NetCom in Chameleon 4.0
   is set for CSLIP.

   If the user wants a PPP account, note that Chameleon 4.0
   does support VJ Header compression and this is automatically
   negotiated at connection time, giving them the equivalent of
   'CPPP'. The user simply specifies a PPP interface in Custom.

2. Verify IP address. (The obvious question.)

3. Host is the first portion of the domain name supplied
   to the user by NetCom.

   (Note that NetCom and NetManage use the term domain
   in slightly different manners.  NetCom standard
   signup info tells the user that their domain is
   <name>.slip.netcom.com.  Chameleon's Custom app
   breaks this down into 'Host' and 'Domain'. So,
   the NetCom provided domain of netman2.slip.netcom.com
   breaks down into Host: netman2,  and Domain:
   slip.netcom.com

4. Domain default is slip.netcom.com

5. Make sure the user has entered the correct Login
   for a SLIP account, and not their shell account.  The
   slip account login will always begin with an "S".
   If the user mistakenly enters their shell account, they
   may appear to connect, but then not be able to get any
   response from the NetCom DNS.

6. Make sure the user is dialing the SLIP phone number,
   and not the shell account phone number.

7. Verify that they have the correct default gateway
   setting.

   A. SLIP Only Connection
   With Chameleon 4.0 they may leave default gateway
   blank if the user has a dial-up only connection.
   All packets will go out over the serial interface.

   Note if the user makes a mistake, like putting their own
   IP address in under default gateway, they will get very
   fast pings, and nothing else. This has happened before.

   B. Simultaneous SLIP and LAN interfaces

   If the user wants to run over multiple interfaces, e.g.
   a simultaneous LAN and SLIP connection, the user should
   specify NO gateway, NO primary interface, and define static
   routes in Custom for up to 5 subnets.

   They need to make sure that they de-select the Ethernet
   interface as their primary interface. This is done under
   the Setup menu in Custom after highlighting the Ethernet
   interface entry in the custom window.  This will remove
   the '*' next to the Ethernet.

   When the SLIP connection is active, it will automatically
   become the default destination. Packets intended for internal
   destinations will be picked up by the static route definitions
   and be sent out over the ethernet card.  When the SLIP
   connection is not active, all packets will go out over the
   Ethernet interface.

8. If the user is experiencing lossy pings, make sure that
   they have selected the proper modem type.  For example,
   selecting a Hayes modem when they have Telebit has been
   noted to produce these symptoms.

9. Verify the script entry in SLIP.INI.  It should
   read similar to the following. (Note that the interface
   name in square brakets may vary depending on the user's
   definition.  NetCom is the name of the pre-defined
   interface configuration in Chameleon 4.0)

[NetCom]
SCRIPT=login: $u$r word: $p$r beginning.... $2$r
TYPE=CSLIP

(Also note, if they just have the script portion thru
to $p$r, they will successfully connect, but not
see the confirmation message that follows.)

A successful connection will appear similar to the
following in the LOG window of Custom:

ATQ0V1E0M1
OK
ATS0=0
OK
ATDT9,241-1528
CONNECT 9600/ARQ/V32/LAPM

login:Snetman2
Snetman2
Password:********

SL/IP session from (192.100.81.110) to 192.187.134.61 beginning....

MAIL Application
----------------
1. Chameleon mail is a multi-user mail client.
   User should first enter as Postmaster and define
   a user for their windows PC.

2. In the user's newly defined mail client:

   Under Settings, Network, Gateway enter MAIL.NETCOM.COM

   Under Settings, Network, Server enter NETCOM<n>.NETCOM.COM
   where <n> is a number between 2 and 9.  You can select any
   of the servers you wish.  If you experience problems
   retrieving your mail, try one of the others.

   For Mail LOGIN and Password the user must put in their
   NetCom SHELL ACCOUNT USERID AND PASSWORD.  No mail
   directory need be specified.  User should select
   'Delete retreived mail from Server' box or they will
   keep re-retrieving old messages.

Note: if the user has changed their Shell Account password
this needs to be reflected here also.

NEWTNews NNTP News Reader Application
-------------------------------------
1. The NetCom NNTP news server address is: nntp.netcom.com

Note: The user's PNC (Personal Network Connection) update
to the NetCom DNS must have occured or it will not validate
the user's address through reverse address resolution and
access to the news server will be denied.
                        # # #
2/10/94
--
Netcom Network Operations -- [phone] -- [e-mail]

Please include original emails referencing the same questions in future
correspondence.

We hope this is helpful information.
Regards,
           /\
**********/@@\ ****************************************
          \__/      NetManage Inc.
       W   AA   W   Home of Chameleon TCPIP for Windows
       |__AYA__/
         AXXV          Suzanne Calkins
         VXXV          Technical Support Representative
      W  VUV   W       [phone]
      |_/ V \_/ __     [phone] fax
           \   [_ \    email: [e-mail]
            \_____/    MIME enclosures are OK

                 gopher server: gopher.netmanage.com
******************************************************



----------End of Original Message----------





>
>>[e-mail]
>
>>I'm also having trouble with Chameleon Sampler (Newt) but, I need to find
>>out if it even supports COMPRESSED PPP. The setup configuration only
>>offers SLIP, CSLIP and PPP. My Internet access is compressed PPP through
>>Netcom. Any help out there would be appreciated. Thanks.....Mike
>
>Does Chameleon have a .cfg for netcom?
>
>I have my unixware ppp server setup for protocol field compression,
>address control field compression and VJ TCP/IP compression and the
Chameleon
>sampler connects just fine. BTW the performance increased markedly
>when i enabled them :->
>
>I didn't have to do anything at the Chameleon end - I only wish that I had
>proper documentation on the Chameleon sampler capabilities.
>
>Craig
>
>--
>| Craig Silva - Swinburne Student Union   \  Appropriate nonsense        |
>| Melbourne, Australia. [phone]    \ about disregarding anything  |
>| [e-mail]             \ my boss says......           |
>| Know thy enemy and know thy friend      \                              |
>

-----------------------------------------------------------------------------
--------
Peggy Liu       of         NetManage, Inc.
10725 N. DeAnza Blvd. Cupertino, CA 95014
Ph: [phone]     [e-mail]
Sent: 05/24/94  19:55:01
(MIME attachments can be received by the Chameleon)
-----------------------------------------------------------------------------
---------




----------End of Original Message----------